Thanks for the patch, but the library follows C/C++ convention for representing octal numbers as documented here:

For integers, when binary, octal, or hexadecimal output is used, this option adds the prefix respective "0b" ("0B"), "0", or "0x" ("0X") to the output value.

It is possible to specify "0o" prefix explicitly of course, e.g. "0o{:o}".

Makes sense.

In the end it's kind of arbitrary, but I would have thought it would match
the python .format semantics (which is more logical IMO).

On Mon, Feb 10, 2014 at 1:37 PM, vitaut [email protected] wrote:

Thanks for the patch, but the library follows C/C++ convention for
representing octal numbers as documented herehttp://zverovich.net/format/
:

For integers, when binary, octal, or hexadecimal output is used, this
option adds the prefix respective "0b" ("0B"), "0", or "0x" ("0X") to the
output value.

It is possible to specify "0o" prefix explicitly of course, e.g. "0o{:o}".

Reply to this email directly or view it on GitHubhttps://github.com//pull/18#issuecomment-34685552
.